Adaptive self-optimizing network using closed-loop feedback

ABSTRACT

Systems, methods, and apparatus for an adaptive self-optimizing network using closed-loop feedback are disclosed. A method for sharing network resources comprises receiving, by a network operations center (NOC), user demand for users from an external network. The method further comprises receiving, by the NOC, key performance indicators from at least one internal network. Also, the method comprises determining, by the NOC, whether at least one internal network has available resources by analyzing the key performance indicators and the user demand. Further, the method comprises allowing, by the NOC when the NOC determines that there are available resources, at least some of the users from the external network to connect to at least one internal network according to the available resources.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a Continuation-In-Part of U.S. patent applicationSer. No. 16/228,627, filed on Dec. 20, 2018, and U.S. patent applicationSer. No. 16/228,678 filed on Dec. 20, 2018, the entire disclosures ofwhich are expressly incorporated by reference herein.

This application claims priority to Australia Patent Application No.2020200945 filed on Feb. 10, 2020, Russia Patent Application No.2020106082 filed on Feb. 10, 2020, Europe Patent Application No.20156478.8 filed on Feb. 10, 2020, China Patent Application No.202010087606.9 filed on Feb. 12, 2020, and Japan Patent Application No.2020-023232 filed on Feb. 14, 2020, the entire disclosures of which areexpressly incorporated by reference herein.

FIELD

The present disclosure relates to networks, such as mobile wireless(e.g., cellular, satellite, tactical military, etc.) networks. Inparticular, the present disclosure relates to adaptive self-optimizingnetworks using closed-loop feedback.

BACKGROUND

Currently, configurations (e.g., payload configurations) of satellitenetworks are changed manually according to changing user demand forsatellite resources (e.g., loading patterns), ambient environmentalconditions, and/or system performance (e.g., including failures). Inparticular, a satellite's payload configuration is changed by a groundstation manually generating and sending payload configuration commandsignals to the satellite. This conventionally used, manual procedure isvery tedious and time consuming for the satellite operator. In addition,since this conventional procedure is manually-driven and does notincorporate closed-loop feedback, there is no self-organization andself-optimization capability.

In light of the foregoing, there is a need for an improved technologyfor adapting configurations to adapt the network to changes in usermobility and capacity demands.

SUMMARY

The present disclosure relates to a method, system, and apparatus for anadaptive self-optimizing network using closed-loop feedback. In one ormore embodiments, a method for an adaptive network of vehicles comprisesreceiving, by a global network operations center (GNOC), operatorinputs. The method further comprises generating, by the GNOC, a globalpolicy according to the operator inputs. Also, the method comprisesgenerating, by the GNOC and/or a local gateway (GW), configurationcommands for configurations for at least one of the vehicles based onthe global policy. In addition, the method comprises transmitting, bythe GNOC and/or the local GW, the configuration commands to at least oneof the vehicles. Additionally, the method comprises transmitting, by thelocal GW, key performance indicators to the GNOC. Also, the methodcomprises revising, by the GNOC, the global policy according to the keyperformance indicators. Further, the method comprises repeating steps ofthe method above that follow the generating of the global policy by theGNOC.

In one or more embodiments, the method further comprises generating, bya regional network operations center (RNOC), a regional policy. In atleast one embodiment, the method further comprises revising, by theGNOC, the global policy according to the regional policy. In someembodiments, the regional policy comprises admission control, mobilitymanagement, channel allocations, carrier allocations, bearerallocations, power management, and/or forward/return (FWD/RTN)scheduling. In one or more embodiments, the RNOC is located within agateway (GW).

In at least one embodiment, the GNOC is located within a gateway (GW).In some embodiments, the global policy comprises beam allocations,capacity allocations, software-defined network (SDN) management, and/oradmission control policy. In one or more embodiments, the operatorinputs comprise frequency spectrum planning, traffic planning, and/orcontingency plans. In some embodiments, the key performance indicatorscomprise subscriber demand, modem power profiles, beam/carrierutilization, session blocking rates, remote access channel (RACH)success rates, bearer success rates, session setup latency, and/orhandover success rates.

In one or more embodiments, the vehicles are space vehicles, airbornevehicles, terrestrial vehicles, or marine vehicles. In at least oneembodiment, the space vehicles are satellites. In some embodiments, thesatellites comprise a geosynchronous earth orbit (GEO) satelliteconstellation, a low earth orbit (LEO) satellite constellation, a mediumearth orbit (MEO) satellite constellation, a super GEO satelliteconstellation, or a hybrid satellite constellation.

In at least one embodiment, the method further comprises generating, bythe GNOC and/or the local GW, extensible markup language (XML) modelsfor the configurations for at least one of the vehicles according to theglobal policy. In some embodiments, the method further comprisesgenerating, by the GNOC and/or the local GW, the configuration commandsaccording to the XML models.

In one or more embodiments, the method further comprises transmitting,by at least one of the vehicles, telemetry to the GNOC and/or the localGW.

In at least one embodiment, a system for an adaptive network of vehiclecomprises a global network operations center (GNOC) configured toreceive operator inputs, to generate a global policy according to theoperator inputs, to generate configuration commands for configurationsfor at least one of the vehicles based on the global policy, and torevise the global policy according to key performance indicators. Thesystem further comprises a local gateway (GW) configured to transmit thekey performance indicators to the GNOC. In one or more embodiments, thelocal gateway (GW) and/or the GNOC are further configured to transmitthe configuration commands to at least one of the vehicles.

In one or more embodiments, the system further comprises a regionalnetwork operations center (RNOC) configured to generate a regionalpolicy. In some embodiments, the GNOC is further configured to revisethe global policy according to the regional policy.

In at least one embodiment, a method for configuring a configuration fora vehicle comprises generating XML models for the configuration for thevehicle. The method further comprises generating configuration commandsfor the vehicle according to the XML models. Further, the methodcomprises configuring the configuration for the vehicle according to theconfiguration commands. In some embodiments, the XML models aregenerated according to a global policy.

In one or more embodiments, a method for sharing network resourcescomprises receiving, by a network operations center (NOC), user demandfor users from an external network. The method further comprisesreceiving, by the NOC, key performance indicators from at least oneinternal network. Also, the method comprises determining, by the NOC,whether at least one internal network has available resources byanalyzing the key performance indicators and the user demand. Further,the method comprises allowing, by the NOC when the NOC determines thatthere are available resources, at least some of the users from theexternal network to connect to at least one internal network accordingto the available resources.

In at least one embodiment, the method further comprises connecting atleast some of the users from the external network to at least oneinternal network via at least one user-to-network interface (UNI). Insome embodiments, the external network is connected to the at least oneinternal network via at least one external network-to-network interface(ENNI). In one or more embodiments, the NOC controls operations of theat least one internal network. In at least one embodiment, when thereare more than one of the internal networks, the internal networks areconnected to each other via at least one internal network-to-networkinterface (INNI). In some embodiments, users from at least one internalnetwork are connected to the at least one internal network via at leastone user-to-network interface (UNI).

In one or more embodiments, the external network and at least oneinternal network each comprise a vehicle, a router, a network operatingsystem (NOS), an open virtual switch (OVS), a backbone edge bridge(BEB), a backbone core bridge (BCB), a virtual network function (VNF),and/or provider backbone bridging-traffic engineering (PBB-TE). In atleast one embodiment, the vehicle is a space vehicle, an airbornevehicle, a terrestrial vehicle, or a marine vehicle. In someembodiments, the space vehicle is a satellite, and the satellite is ageosynchronous earth orbit (GEO) satellite, a low earth orbit (LEO)satellite, a medium earth orbit (MEO) satellite, or a super GEOsatellite.

In at least one embodiment, a software defined network (SDN) controllerof the NOC controls connections of at least one externalnetwork-to-network interface (ENNI), at least one internalnetwork-to-network interface (INNI), and at least one user-to-networkinterface (UNI).

In one or more embodiments, a system for sharing network resourcescomprises an external network, and at least one internal network. Thesystem further comprises a network operations center (NOC) configured toreceive user demand for users from the external network, to receive keyperformance indicators from at least one internal network, to determinewhether at least one internal network has available resources byanalyzing the key performance indicators and the user demand, and toallow, when the NOC determines that there are available resources, atleast some of the users from the external network to connect to at leastone internal network according to the available resources.

In at least one embodiment, at least some of the users from the externalnetwork are connected to at least one internal network via at least oneuser-to-network interface (UNI). In one or more embodiments, the NOC isconfigured to control operations of the at least one internal network.In one or more embodiments, a software defined network (SDN) controllerof the NOC is configured to control connections of at least one externalnetwork-to-network interface (ENNI), at least one internalnetwork-to-network interface (INNI), and at least one user-to-networkinterface (UNI).

The features, functions, and advantages can be achieved independently invarious embodiments of the present disclosure or may be combined in yetother embodiments.

DRAWINGS

These and other features, aspects, and advantages of the presentdisclosure will become better understood with regard to the followingdescription, appended claims, and accompanying drawings where:

FIG. 1 is a block diagram showing the management architecture for thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure.

FIG. 2 is a block diagram showing the distributed functionalarchitecture for the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback, in accordance with at least oneembodiment of the present disclosure.

FIGS. 3A and 3B together form a flow chart showing the method foroperation of the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback relating to FIG. 1, in accordancewith at least one embodiment of the present disclosure.

FIG. 4 is a diagram showing the top level architecture for the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback, in accordance with at least one embodiment of the presentdisclosure.

FIG. 5 is a diagram showing further details of the operations manager ofFIG. 4, in accordance with at least one embodiment of the presentdisclosure.

FIG. 6 is a flow chart showing the method for operation of the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback relating to FIG. 4, in accordance with at least one embodimentof the present disclosure.

FIG. 7 is a flow chart showing the method for configuring aconfiguration for a network access node relating to FIG. 5, inaccordance with at least one embodiment of the present disclosure.

FIG. 8 is a block diagram showing the management architecture for thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure.

FIG. 9 is a block diagram showing the distributed functionalarchitecture for the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback, in accordance with at least oneembodiment of the present disclosure.

FIGS. 10A and 10B together form a flow chart showing the method foroperation of the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback relating to FIG. 8, in accordancewith at least one embodiment of the present disclosure.

FIG. 11 is a diagram showing the top level architecture for thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure.

FIG. 12 is a diagram showing further details of the operations managerof FIG. 11, in accordance with at least one embodiment of the presentdisclosure.

FIG. 13 is a flow chart showing the method for operation of thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback relating to FIG. 11, in accordance with at leastone embodiment of the present disclosure.

FIG. 14 is a flow chart showing the method for configuring aconfiguration for a vehicle relating to FIG. 12, in accordance with atleast one embodiment of the present disclosure.

DESCRIPTION

The methods and apparatus disclosed herein provide an operative systemfor an adaptive self-optimizing network using closed-loop feedback. Inone or more embodiments, the system of the present disclosure providesadaptive, closed-loop management of a network (e.g., a satellitenetwork) in a manner that allows for the network to dynamically adapt tochanging user demand for network resources (e.g., loading patterns),ambient environmental conditions, and/or system performance (e.g.,including failures). In particular, the disclosed system allows formanagement of network resources by using closed-loop feedback ofreal-time statistics pulled from the system.

Specifically, a distributed microservices-based architecture is employedby the system to disseminate a centralized policy (e.g., a globalpolicy) from a global network operations center (GNOC) to a collectionof gateways (GWs) (e.g., ground stations) located throughout the system.Additionally, the system employs a system resource manager (SRM) thatprovides essential functions for connection management, beam management,carrier management, admission control, routing management, signalingmanagement, and/or automated system configuration. The centralizedpolicy, which is disseminated to the gateways, is derived from keyperformance indicators (KPIs) pulled from various elements of the systemto create a closed-loop, adaptive feedback mechanism.

In addition, standards-based protocols and interfaces are employed forevolvability and interoperability of the network. Extensible markuplanguage (XML) based schemas developed to model the network accessnode's configuration (e.g., satellite payload configuration) areutilized by the system to allow the network access nodes (e.g.,satellites) residing in the network (e.g., constellation) to be managedseamlessly as part of the network via an operations manager. Theadaptive nature of the disclosed system allows for the network ofnetwork access nodes (e.g., satellite constellation) to behave as aself-organizing and self-optimizing network.

The system of the present disclosure has the following advantageousfeatures. Firstly, the system employs adaptive, closed-loop feedbackfrom the network to dynamically self-optimize performance. Secondly, thesystem provides tight integration of all of the essential functionsrequired for system resource management of a large nodal network (e.g.,satellite network). Thirdly, the system provides a reusable frameworkarchitecture that can be applied to a single satellite system, aconstellation of satellites (e.g., a geosynchronous earth orbit (GEO)satellite constellation, a low earth orbit (LEO) satelliteconstellation, a medium earth orbit (MEO) satellite constellation, or asupersynchronous GEO satellite constellation, with no inclination orwith inclination), or a hybrid satellite constellation comprisingmultiple different satellite constellations (e.g., a GEO and MEOsatellite constellation, a LEO and MEO satellite constellation, or a GEOand LEO satellite constellation). And, fourthly, the disclosed systemhas the ability to optimize system policy based on dynamic feedback andgenerate system configuration commands that can be automatically pushedthroughout the network in real time.

In the following description, numerous details are set forth in order toprovide a more thorough description of the system. It will be apparent,however, to one skilled in the art, that the disclosed system may bepracticed without these specific details. In the other instances, wellknown features have not been described in detail, so as not tounnecessarily obscure the system.

Embodiments of the present disclosure may be described herein in termsof functional and/or logical components and various processing steps. Itshould be appreciated that such components may be realized by any numberof hardware, software, and/or firmware components configured to performthe specified functions. For example, an embodiment of the presentdisclosure may employ various integrated circuit components (e.g.,memory elements, digital signal processing elements, logic elements,look-up tables, or the like), which may carry out a variety of functionsunder the control of one or more processors, microprocessors, or othercontrol devices. In addition, those skilled in the art will appreciatethat embodiments of the present disclosure may be practiced inconjunction with other components, and that the systems described hereinare merely example embodiments of the present disclosure.

For the sake of brevity, conventional techniques and components relatedto networks, and other functional aspects of the system (and theindividual operating components of the systems) may not be described indetail herein. Furthermore, the connecting lines shown in the variousfigures contained herein are intended to represent example functionalrelationships and/or physical couplings between the various elements. Itshould be noted that many alternative or additional functionalrelationships or physical connections may be present in one or moreembodiments of the present disclosure.

In various embodiments, the disclosed system for an adaptiveself-optimizing network using closed-loop feedback employs aconstellation of satellites. It should be noted that the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback may be employed for network access nodes (e.g., high-altitudeplatforms, airborne vehicles, terrestrial vehicles, marine vehicles,and/or fixed terrestrial base stations) other than satellites asdisclosed herein. The following discussion is thus directed tosatellites without loss of generality.

FIG. 1 is a block diagram 100 showing the management architecture forthe disclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure. In this figure, a network access node constellation110 comprises a system of interconnected configurable network accessnodes 105. In one or more embodiments, the network access nodes 105 maybe space vehicles (e.g., satellites, high-altitude platforms (HAPs),such as balloons or high-endurance unmanned aerial vehicles (UAVs)),airborne vehicles (e.g., aircraft or unmanned aerial vehicle (UAVs)),terrestrial vehicles (trucks, tanks, or unmanned ground vehicles(UGVs)), marine vehicles (e.g., ships, submarines, or an unmannedunderwater vehicles (UUVs)), and/or fixed terrestrial based stations. Insome embodiments, when the network access node constellation 110 is aconstellation of satellites, the satellite constellation may be ageosynchronous earth orbit (GEO) satellite constellation (with noinclination or with inclination), a low earth orbit (LEO) satelliteconstellation (with no inclination or with inclination), a medium earthorbit (MEO) satellite constellation (with no inclination or withinclination), a supersynchronous GEO satellite constellation (with noinclination or with inclination), or a hybrid satellite constellationcomprising multiple different satellite constellations (e.g., a GEO andMEO satellite constellation, a LEO and MEO satellite constellation, or aGEO and LEO satellite constellation) (with no inclination or withinclination). It should be noted that when the network access nodes 105are satellites, the satellites will each have a configurable payload115.

Also in this figure, a global network operations center (GNOC) is shownto comprise an operation center (xOC) 125 (that is unique to the type ofnetwork the network access nodes use), a network operations center (NOC)130, and a cybersecurity operations center (CSOC) 135. The xOC 125, ifone or more of the network access nodes 105 is a satellite, maintainsthe orbit of the satellite, receives tracking and telemetry (e.g.,regarding the satellite's location, configuration, and state of health),transmits commands (e.g., satellite bus and payload configurationcommands, and manages antenna pointing). The CSOC 135 manages thesecurity of the system (e.g., by detecting, notifying of, and mitigatingcyber attacks). The NOC 130 comprises a system resource manager (SRM)140 that manages the resources of the network of network access nodes.

Also in FIG. 1, at least one distributed network gateway (GW) 145 isshown. Each of the at least one distributed network GW 145 is associatedwith at least one of the network access nodes 105, and each of thenetwork access nodes 105 is associated with the at least one distributednetwork GW 145. Each of the at least one distributed network GW 145 isshown to comprise an SRM 150 for GW monitoring and control (M&C) 155. Inaddition, each of the at least one distributed network GW 145 comprisesan antenna farm (e.g., a plurality of transmit and receive antennas)160, radio frequency equipment (RFE) and switching 165, MODEMs(modulator/demodulator) and optionally a ground-based beamforming (GBBF)network 170, and network architecture/infrastructure 175 (e.g.,switches, routers, firewalls, etc.). The GW M&C 155 performs monitoringand control of the state of health of the antennas and RFE, networkinfrastructure, and/or control of the feederlink antennas of the antennafarm. Each of the at least one distributed network GW 145 is incommunication (via fiber (wire) and/or wirelessly (via satellite)) withthe GNOC 120 and may also be in communication (via fiber (wire) and/orwirelessly (via satellite, e.g., by feeder-link)) with its collection ofthe network access nodes 105 attached.

In addition, the disclosed system may comprise a regional NOC (RNOC)180, as is shown in FIG. 1. The RNOC 180 comprises a SRM 185. The RNOC180 is in communication (via fiber (wire) and/or wirelessly (viasatellite)) with the GNOC 120 and/or is in communication (via fiber(wire) and/or wirelessly (via satellite)) with the at least onedistributed network GW 145.

The GNOC 120 and RNOC 180 may each be co-located with (or within) adistributed network GW. As such, the GNOC 120 and the RNOC 180 may alsocomprise the same units (e.g., the antenna farm 160, RFE and switching165, MODEMs and optional GBBF 170, and networkarchitecture/infrastructure 175) as the at least one distributed networkGW 145 as depicted in FIG. 1. As such, the SRM 140 of the GNOC 120 andthe SRM 150 of the RNOC may perform GW M&C 155 by monitoring and controlof the state of health of the antennas and RFE, network infrastructure,and/or control of the feederlink antennas of the antenna farm.

During operation of the disclosed system, the SRM 140 of the GNOC 120receives operator inputs 190 from operators (e.g., refer to 410 of FIG.4). The operator inputs 190 may comprise frequency spectrum planning,traffic planning, and/or contingency plans. The SRM 140 of the GNOC 120generates a (initial) global policy 191 according to the parameters ofthe operator inputs 190. The global policy 191 may comprise beamallocations (e.g., the size, shape, location, and power of the antennabeams), capacity allocations (e.g., the location of terminals (users)and user demands), software-defined network (SDN) management (e.g., therouting and signaling policy), and/or admission control policy (e.g.,connection admission control (CAC) policy, which dictates the adding orremoving of terminals (users)).

After the SRM 140 generates the global policy 191, the SRM 140 of theGNOC 120 and/or an SRM 150 of the at least one distributed network GW145 generates configuration commands 192 for configurations for theconfigurable payload 115 of at least one of the network access nodes 105in the network access node constellation 110 based on the global policy191.

It should be noted that in some embodiments, alternatively, anoperations manager (refer to 420 of FIG. 5) may generate XML models(refer to 520 a, 520 b, 520 c, 520 d, 520 n of FIG. 5) forconfigurations for the configurable payload 115 in accordance with thedefined global policy 191. For these embodiments, an XML-basedconfiguration data translator (refer to 510 of FIG. 5) translates theXML models 520 a, 520 b, 520 c, 520 d, 520 n into flight softwarecommands to generate the configuration commands 192. The description ofFIG. 5 discusses the details of the use of XML models 520 a, 520 b, 520c, 520 d, 520 n to generate the configuration commands 192. It should benoted that the operations manager 420 and the XML-based configurationdata translator 510 may be located within the GNOC 120, the RNOC 180,and/or at the least one distributed network GW 145. In particular, theoperations manager 420 and the XML-based configuration data translator510 may be located within the SRM 140 of the GNOC 120, the SRM 185 ofthe RNOC 180, and/or the SRM 150 of the at least one distributed networkGW 145.

After the configuration commands 192 have been generated, the xOC 125 ofthe GNOC 120, the RNOC 180, and/or the at least one distributed networkGW 145 transmits the configuration commands (CMD) 192 to at least one ofthe network access nodes 105 to configure the configurable payload 115of the at least one of the network access nodes 105 accordingly. Afterthe at least one of the network access nodes 105 receives theconfiguration commands 192, the configuration commands 192 command theconfigurable payload 115 of the at least one of the network access nodes105 to configure the configurable payload 115 according to theconfiguration(s) contained within the configuration commands 192.

After the configurable payload 115 of the at least one of the networkaccess nodes 105 has configured according to the configuration commands192, the at least one of the network access nodes 105 will transmittelemetry (TLM) (e.g., comprising the configurable payload 115configuration, monitoring information, and the state of health of thenetwork access nodes 105) 193 to the xOC 125 of the GNOC 120, the RNOC180, and/or the at least one distributed network GW 145.

Then, the at least one distributed network GW 145 and/or the RNOC 180will transmit a summary of key performance indicators (KPIs) 194, whichare obtained from at least one of the network access nodes 105 to theGNOC 120. The summary of KPIs 194 may comprise subscriber demand, MODEMpower profiles, beam and carrier (beam/carrier) utilization, sessionblocking rates, random access channel (RACH) success rates (e.g., thesuccess rates of the RACH procedure used to allow user terminals todiscover and negotiate access to the system), bearer success rates(e.g., the success rates of bearer requests), session setup latency(e.g., length of time to establish a link), and/or handover success rate(e.g., the success rates for beam-to-beam, inter-network access node(e.g., satellite-to-satellite), inter-gateways (e.g., GW-to-GW), and/orinter-network (e.g., internal-to-internal network orexternal-to-external network, also referred to as roaming) handover).

In some embodiments, optionally, the RNOC 180 will generate a regionalpolicy 195. The regional policy 195 may comprise admission control,mobility management, channel allocations, carrier allocations, bearerallocations, power management, and/or forward and/or return (FWD/RTN)scheduling (e.g., downlink/uplink scheduling for user terminals). Forthese embodiments, the RNOC 180 will transmit the regional policy 195 tothe GNOC 120, either directly or via the at least one distributednetwork GW 145.

After the GNOC 120 has received the summary of KPIs 194, the GNOC 120may revise (update) the global policy 191 according to the summary ofKPIs 194 and, if necessary, according to the regional policy 195, inorder to dynamically adapt resource allocations to changes in theaggregate subscriber demand.

After the GNOC 120 has revised the global policy 191, the operation ofthe system repeats the steps following the GNOC 120 initially generatingthe global policy 191. As such, the network of the network access nodes105 is self-optimizing by using closed-loop feedback of KPIs 194 (andoptionally the regional policy 195) provided by the at least onedistributed network GW 145 and/or the RNOC 180.

FIG. 2 is a block diagram 200 showing the distributed functionalarchitecture for the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback, in accordance with at least oneembodiment of the present disclosure. In this figure, GNOC functions 210and distributed network GW functions 220 are illustrated. The GNOCfunctions 210 are functions of the GNOC 120 (refer to FIG. 1), and thedistributed network GW functions 220 are functions of the at least onedistributed network GW 145 (refer to FIG. 1) and/or the RNOC 180 (referto FIG. 1). As shown in this figure, the GNOC functions 210 comprise amessage queue 205 and a non-structured query language (NoSQL) database215. In addition, the GNOC functions 210 comprise connection management225 (e.g., for establishing connections from a user terminal to thenetwork access nodes 105 within view of the user terminal and to the atleast one distributed network GW 145 through the network access nodes105), beam management 235 (e.g., controlling the beamformer, which isphysically located either within the network access nodes 105 or withinthe at least one distributed network GW 145), and carrier management 245(e.g., controlling the MODEM carriers within a beam). The GNOC functions210 also comprise a connection admission control (CAC) policy 230 (e.g.,a network configuration policy (e.g., the global policy 191) generatedbased on user demand and available resources), routing management 240(e.g., controlling the routing of the signal traffic through thenetwork), and signaling management 250 (e.g., setting up sessions forthe routing).

Also in this figure, a resource manager gateway 285 allows for the GNOC120 to communicate with the at least one distributed network GW 145 (orthe RNOC 180) via JavaScript Object Notification (JSON) and/or standardweb-based interfaces (e.g., represented state transfer (REST), hypertexttransfer protocol (HTTP), and/or websocket).

As shown in this figure, the distributed network GW functions 220comprise payload configuration (P/L CFG) 255 (e.g., for configuration ofthe payload), forward link control (F/L CTRL) 265 (e.g., for controllingthe link between the network access nodes 105 and the at least onedistributed network GW 145 (or the RNOC 180)), MODEM control 275 (e.g.,controlling the MODEM, which creates the carriers), connection admissioncontrol (CAC) 260 (e.g., controlling the adding or removing of userterminals based on the CAC policy 230 (e.g., global policy 191)),mobility 270 (e.g., controlling the handover of network access nodes asthey move and/or of user terminals as they move), and software-definednetwork (SDN) control 280 (e.g., the routing of signals according to theCAC policy 230).

FIGS. 3A and 3B together form a flow chart showing the method foroperation of the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback relating to FIG. 1, in accordancewith at least one embodiment of the present disclosure. At the start 310of the method, a global network operations center (GNOC) receivesoperator inputs 320. Then, the GNOC generates a global policy accordingto the operator inputs 330.

The GNOC and/or a distributed network gateway (GW) generateconfiguration commands for configurations for at least one of thenetwork access nodes based on the global policy. Then, the GNOC and/orthe distributed network GW transmit the configuration commands to atleast one of the network access nodes 350. At least one of the networkaccess nodes then transmits telemetry to the GNOC and/or the distributednetwork GW 360.

Then, a distributed network GW transmits a summary of key performanceindicators (KPIs) to the GNOC 370. Optionally, a regional networkoperations center (RNOC) generates a regional policy 380. The GNOC thenrevises the global policy according to the summary of key performanceindicators and, if necessary, according to the regional policy 390.Then, the method repeats itself by proceeding back to step 340.

FIG. 4 is a diagram 400 showing the top level architecture for thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure. In this figure, a network operations center (NOC)430 is shown. The NOC 430 may be a GNOC 120 or a RNOC 180, and may beco-located within a distributed network GW. The NOC 430 is shown tocomprise an operational support system/business support system (OSS/BSS)425 and the operations manager 420. The operations manager 420 comprisesan application programming interface (API) handler 435, a database 440,a SRM policy enforcement module 445, a lifecycle services orchestration(LSO) manager 450, and a service and configuration registry 455. Theoperations manager 420 further comprises an operator interface (I/F) 490that is used to provide situational awareness to the NOC 430 and theoperations manager 420 access to operators residing within the NOC 430.In addition, the operations manager 420 may operate within the contextof a commercial operating system, such as LINUX 460.

The NOC 430 also comprises a software-defined network (SDN) controller465, which communicates with the operations manager 420 by using astandard network management system-software-defined network controller(NMS-SDNC) application program interface (API).

Also shown in this figure are an external network 471 and internalnetworks 470 a, 470 b. It should be noted that the system may comprisemore or less than two internal networks 470 a, 470 b, and/or more thanone external network 471 as is shown in this figure. The NOC 430controls operations of the internal networks 470 a, 470 b, and theexternal network 471 is controlled by a different entity.

The external network (Domain B (Peer)) 471 is shown to comprise anetwork operating system (NOS) 480 and two routers 475 a, 475 b. Inpractice, the external network 471 domain may employ alternativearchitectures than as shown. The NOS 480 and the two routers 475 a, 475b are all in communication with each other within the external network471. Users 479 associated with the external network 471 are connected tothe external network 471 via a user-to-network interface (UNI) 486 d.

The internal network (Domain A₁) 470 a is shown to comprise a backbonecore bridge (BCB) 481, a virtual network function (VNF) 476, at leastone of the network access nodes (e.g., satellite) 105, a providerbackbone bridging-traffic engineering (PBB-TE) 477, and two backboneedge bridges (BEBs) 482 a, 482 b. In practice, the internal network 470a domain may employ alternative architectures than as shown. The BCB481, VNF 476, the at least one of the network access nodes 105, PBB-TE477, and BEBs 482 a, 482 b are all in communication with each otherwithin the internal network 470 a.

The internal network (Domain A₂) 470 b is shown to comprise three openvirtual switches (OVSs) 483 a, 483 b, 483 c. In practice, the internalnetwork 470 b domain may employ alternative architectures than as shown.The OVSs 483 a, 483 b, 483 c are all in communication with each otherwithin the internal network 470 b. Users 478 associated with theinternal networks 470 a, 470 b are connected to the internal networks470 a, 470 b via user-to-network interfaces (UNIs) 486 a, 486 b.

The external network 471 is connected to internal network 470 a and tointernal network 470 b via external network-to-network interfaces(ENNIs) 484 a, 484 b, 484 c. Internal network 470 a is connected tointernal network 470 b via internal network-to-network interfaces(INNIs) 485 a, 485 b.

It should be noted that the external network 471 and internal networks470 a, 470 b may each comprise various different components in variousdifferent combinations than as shown in FIG. 4. In particular, theexternal network 471 and the internal networks 470 a, 470 b may eachcomprise at least one of the network access nodes 105, a router 475, anetwork operating system (NOS) 480, an open virtual switch (OVS) 483, abackbone edge bridge (BEB) 482, a backbone core bridge (BCB) 481, avirtual network function (VNF) 476, and/or provider backbonebridging-traffic engineering (PBB-TE) 477. The at least one of thenetwork access nodes 105 may be a space vehicle, a high-altitudeplatform, an airborne vehicle, a terrestrial vehicle, or a marinevehicle. In some embodiments, the space vehicle is a satellite, and thesatellite is a geosynchronous earth orbit (GEO) satellite, a low earthorbit (LEO) satellite, a medium earth orbit (MEO) satellite, or asupersynchronous GEO satellite.

During operation of the disclosed system, the operations manager 420 ofthe NOC 430 receives a user demand from the external network 470. Theaccess requests with user demand, which specifies a desired amount ofresources (e.g., bandwidth, etc.) from the internal networks 470 a, 470b to be used by (shared with) users 479 associated with the externalnetwork 471. The operations manager 420 of the NOC 430 also receives asummary of KPIs from at least one of the internal networks 470 a, 470 b.

After the operations manager 420 of the NOC 430 receives the user demandand the summary of KPIs, the operations manager 420 of the NOC 430analyzes the user demand from the access requests and the summary ofKPIs to determine whether at least one of the internal networks 470 a,470 b has available resources that can be shared with the users 479,while maintaining enforcement of pre-existing service contracts withexisting users. When the operations manager 420 of the NOC 430determines that at least one of the internal networks 470 a, 470 b hasavailable resources, the operations manager 420 of the NOC 430 willnotify the SDN controller 465 of the NOC 430 to allow the users 479associated with the external network 471 to connect to the internalnetworks 470 a, 470 b according to the available resources. The SDNcontroller 465 of the NOC 430 will then allow a specific number of users479 to connect to the internal networks 470 a, 470 b according to theamount of available resources. Then, the users 479 that are allowed toconnect to the internal networks 470 a, 470 b will proceed to connect tothe internal networks 470 a, 470 b via UNI 486 c.

It should be noted that the SDN controller 465 of the NOC 430 controlsconnections (switching) of the ENNIs 484, the INNIs 485, and the UNIs486 of the system, in addition to intra-domain connectivity.

FIG. 5 is a diagram 500 showing further details of the operationsmanager 420 of FIG. 4, in accordance with at least one embodiment of thepresent disclosure. In this figure, the operations manager 420 is shownto comprise the database (e.g., system configuration database) 440(refer to FIG. 4) and further comprise an XML-based configuration datatranslator 510. The database 440 comprises a startup configuration (Cfg)database 515, a running configuration database 525, and a candidateconfiguration database 535. The database 440 receives policy managementinformation, network topology information, service managementinformation, and network state of health and performance information tobe stored within its databases 515, 525, 535.

During operation of the disclosed system, the operations manager 420generates XML models 520 a, 520 b, 520 c, 520 d, 520 n forconfigurations for units (e.g., switches 530 a, routers 530 b, MODEMs530 c, and other devices 530 d) for the configurable payload 115 (referto FIG. 1) according to the global policy 191 (refer to FIG. 1). Afterthe XML models 520 a, 520 b, 520 c, 520 d, 520 n have been generated,the XML-based configuration data translator 510 operates as a payloadconfigurator 540, which is a translator to translate the XML models 520a, 520 b, 520 c, 520 d, 520 n into proprietary flight software commandsto be used as the configuration commands 192 (refer to FIG. 1).

FIG. 6 is a flow chart showing the method for operation of the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback relating to FIG. 4, in accordance with at least one embodimentof the present disclosure. At the start 610 of the method, a networkoperations center (NOC) receives access requests for users subscribed toan external network 620. Then, the NOC receives a summary of keyperformance indicators (KPIs) from at least one internal network 630.The NOC then determines whether at least one internal network hasavailable resources by analyzing the summary of key performanceparameters and the user demand 640. When the NOC determines that thereare available resources (while maintaining enforcement of pre-existingservice contracts with existing users), the NOC allows at least some ofthe users from the external network to connect to at last one internalnetwork to the available resources 650. Then, at least some of the usersfrom the external network connect to at least one internal network viaat least one user-to-network interface (UNI) 660. Then, the method ends670.

FIG. 7 is a flow chart showing the method for configuring aconfiguration for a network access node relating to FIG. 5, inaccordance with at least one embodiment of the present disclosure. Atthe start 710 of the method, XML models are generated for theconfiguration for the network access node 720. Then, configurationcommands are generated for the network access node according to XMLmodels 730. The configuration of the network access node is thenconfigured according to the configuration commands 740. Then, the methodends 750.

In addition, the methods and apparatus disclosed herein provide anoperative system for an adaptive self-optimizing network usingclosed-loop feedback. In one or more embodiments, the system of thepresent disclosure provides adaptive, closed-loop management of asatellite network in a manner that allows for the network to dynamicallyadapt to changing user demand for satellite resources (e.g., loadingpatterns), ambient environmental conditions, and/or system performance(e.g., including failures). In particular, the disclosed system allowsfor management of satellite resources by using closed-loop feedback ofreal-time statistics pulled from the system.

Specifically, a distributed microservices-based architecture is employedby the system to disseminate a centralized policy (e.g., a globalpolicy) from a global network operations center (GNOC) to a collectionof ground stations (e.g., ground gateways (GWs)) located throughout thesystem. Additionally, the system employs a system resource manager (SRM)that provides essential functions for connection management, beammanagement, carrier management, admission control, routing management,signaling management, and/or automated system configuration. Thecentralized policy, which is disseminated to the ground stations, isderived from key performance indicators (KPIs) pulled from variouselements of the system to create a closed-loop, adaptive feedbackmechanism.

Further, standards-based protocols and interfaces are employed forevolvability and interoperability of the network. Extensible markuplanguage (XML) based schemas developed to model the satellite payloadare utilized by the system to allow the satellite payloads residing inthe constellation to be managed seamlessly as part of the network via anoperations manager. The adaptive nature of the disclosed system allowsfor the satellite constellation to behave as a self-organizing andself-optimizing network.

The system of the present disclosure has the following advantageousfeatures. Firstly, the system employs adaptive, closed-loop feedbackfrom the network to dynamically self-optimize performance. Secondly, thesystem provides tight integration of all of the essential functionsrequired for system resource management of a large satellite network.Thirdly, the system provides a reusable framework architecture that canbe applied to a single satellite system, a constellation of satellites(e.g., a geosynchronous earth orbit (GEO) satellite constellation, a lowearth orbit (LEO) satellite constellation, a medium earth orbit (MEO)satellite constellation, or a super GEO satellite constellation, with noinclination or with inclination), or a hybrid satellite constellationcomprising multiple different satellite constellations (e.g., a GEO andMEO satellite constellation, a LEO and MEO satellite constellation, or aGEO and LEO satellite constellation). And, fourthly, the disclosedsystem has the ability to optimize system policy based on dynamicfeedback and generate system configuration commands that can beautomatically pushed throughout the network in real time.

In the following description, numerous details are set forth in order toprovide a more thorough description of the system. It will be apparent,however, to one skilled in the art, that the disclosed system may bepracticed without these specific details. In the other instances, wellknown features have not been described in detail, so as not tounnecessarily obscure the system.

Embodiments of the present disclosure may be described herein in termsof functional and/or logical components and various processing steps. Itshould be appreciated that such components may be realized by any numberof hardware, software, and/or firmware components configured to performthe specified functions. For example, an embodiment of the presentdisclosure may employ various integrated circuit components (e.g.,memory elements, digital signal processing elements, logic elements,look-up tables, or the like), which may carry out a variety of functionsunder the control of one or more processors, microprocessors, or othercontrol devices. In addition, those skilled in the art will appreciatethat embodiments of the present disclosure may be practiced inconjunction with other components, and that the systems described hereinare merely example embodiments of the present disclosure.

For the sake of brevity, conventional techniques and components relatedto networks, and other functional aspects of the system (and theindividual operating components of the systems) may not be described indetail herein. Furthermore, the connecting lines shown in the variousfigures contained herein are intended to represent example functionalrelationships and/or physical couplings between the various elements. Itshould be noted that many alternative or additional functionalrelationships or physical connections may be present in one or moreembodiments of the present disclosure.

In various embodiments, the disclosed system for an adaptiveself-optimizing network using closed-loop feedback employs aconstellation of satellites. It should be noted that the disclosedsystem for an adaptive self-optimizing network using closed-loopfeedback may be employed for other vehicles (e.g., airborne vehicles,terrestrial vehicles, and marine vehicles) other than satellites asdisclosed herein. The following discussion is thus directed tosatellites without loss of generality.

FIG. 8 is a block diagram 800 showing the management architecture forthe disclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure. In this figure, a vehicle constellation 810comprises a network of configurable vehicles 805. In one or moreembodiments, the vehicles 805 may be space vehicles (e.g., satellites),airborne vehicles (e.g., an aircraft or an unmanned aerial vehicles(UAVs)), terrestrial vehicles (trucks, tanks, or unmanned groundvehicles (UGVs)), and/or marine vehicles (e.g., ships, submarines, or anunmanned underwater vehicles (UUVs)). In some embodiments, when thevehicle constellation 810 is a constellation of satellites, thesatellite constellation may be a geosynchronous earth orbit (GEO)satellite constellation (with no inclination or with inclination), a lowearth orbit (LEO) satellite constellation (with no inclination or withinclination), a medium earth orbit (MEO) satellite constellation (withno inclination or with inclination), a super GEO satellite constellation(with no inclination or with inclination), or a hybrid satelliteconstellation comprising multiple different satellite constellations(e.g., a GEO and MEO satellite constellation, a LEO and MEO satelliteconstellation, or a GEO and LEO satellite constellation) (with noinclination or with inclination). It should be noted that when thevehicles 805 are satellites, the satellites will each have aconfigurable payload 815.

Also in this figure, a global network operations center (GNOC) is shownto comprise a vehicle operation center (VOC) 825, a network operationscenter (NOC) 830, and a cybersecurity operations center (CSOC) 835. TheVOC 825, if one of the vehicles 805 is a satellite, maintains the orbitof the satellite, receives telemetry (e.g., regarding the vehicle'spayload configuration and state of health), transmits commands (e.g.,payload configuration commands, and manages antenna pointing. The CSOC835 manages the security of the system (e.g., by detecting, notifyingof, and mitigating cyber attacks). The NOC 830 comprises a systemresource manager (SRM) 840 that manages the resources of the network ofvehicles.

Also in FIG. 8, at least one local gateway (GW) 845 is shown. Each ofthe at least one local GW 845 is associated with at least one of thevehicles 805, and each of the vehicles 805 is associated with the atleast one local GW 845. Each of the at least one local GW 845 is shownto comprise a SRM 850 for GW monitoring and control (M&C) 855. Inaddition, each of the at least one local GW 845 comprises an antennafarm (e.g., a plurality of transmit and receive antennas) 860, radiofrequency equipment (RFE) and switching 865, MODEMs(modulator/demodulator) and optionally a ground-based beamformer (GBBF)870, and network architecture/infrastructure 875 (e.g., switches,routers, firewalls, etc.). The GW M&C 855 performs monitoring of thestate of health of the antennas and RFE, switching of the networkswitches, and/or gimballing of the antennas of the antenna farm. Each ofthe at least one local GW 845 is in communication (via wire and/orwirelessly) with the GNOC 820 and may also be in communication (via wireand/or wirelessly, e.g., by feeder-link) with its associated one of thevehicles 805.

In addition, the disclosed system may comprise a regional NOC (RNOC)880, as is shown in FIG. 8. The RNOC 880 comprises a SRM 885. The RNOC880 is in communication (via wire and/or wirelessly) with the GNOC 820and/or is in communication (via wire and/or wirelessly) with the atleast one local GW 845.

The GNOC 820 and RNOC 880 may each be located within a GW. As such, theGNOC 820 and the RNOC 880 may also comprise the same units (e.g., theantenna farm 860, RFE and switching 865, MODEMs and optional GBBF 870,and network architecture/infrastructure 875) as the at least one localGW 845 as depicted in FIG. 8. As such, the SRM 840 of the GNOC 820 andthe SRM 850 of the RNOC may perform GW M&C 855 by monitoring of thestate of health of the antennas and RFE, switching of the networkswitches, and gimballing of the antennas of the antenna farm.

During operation of the disclosed system, the SRM 840 of the GNOC 820receives operator inputs 890 from operators (e.g., refer to 1110 of FIG.11). The operator inputs 890 may comprise frequency spectrum planning,traffic planning, and/or contingency plans. The SRM 840 of the GNOC 820generates a (initial) global policy 891 according to the parameters ofthe operator inputs 890. The global policy 891 may comprise beamallocations (e.g., the size, shape, location, and power of the antennabeams), capacity allocations (e.g., the location of terminals (users)and user demands), software-defined network (SDN) management (e.g., therouting and signaling policy), and/or admission control policy (e.g.connection admission control (CAC) policy, which dictates the adding orremoving of terminals (users)).

After the SRM 840 generates the global policy 891, the SRM 840 of theGNOC 820 and/or an SRM 850 of the at least one local GW 845 generatesconfiguration commands 892 for configurations for the configurablepayload 815 of at least one of the vehicles 805 in the vehicleconstellation 810 based on the global policy 891.

It should be noted that in some embodiments, alternatively, anoperations manager (refer 1120 of FIG. 12) may generate XML models(refer to 1220 a, 1220 b, 1220 c, 1220 d, 1220 n of FIG. 12) forconfigurations for the configurable payload 815 according to the globalpolicy 891. For these embodiments, an XML-based configuration datatranslator (refer to 1210 of FIG. 12) translates the XML models 1220 a,1220 b, 1220 c, 1220 d, 1220 n into flight software commands to generatethe configuration commands 892. The description of FIG. 12 discusses thedetails of the use of XML models 1220 a, 1220 b, 1220 c, 1220 d, 1220 nto generate the configuration commands 892. It should be noted that theoperations manager 1120 and the XML-based configuration data translator1210 may be located within the GNOC 820, the RNOC 880, and/or the atleast one local GW 845. In particular, the operations manager 1120 andthe XML-based configuration data translator 1210 may be located withinthe SRM 840 of the GNOC 820, the SRM 885 of the RNOC 880, and/or the SRM850 of the at least one local GW 845.

After the configuration commands 892 have been generated, the VOC 825 ofthe GNOC 820, the RNOC 880, and/or the at least one local GW 845transmits the configuration commands (CMD) 892 to at least one of thevehicles 805 to configure the configurable payload 815 of the at leastone of the vehicles 805 accordingly. After the at least one of thevehicles 805 receives the configuration commands 892, the configurationcommands 892 command the configurable payload 815 of the at least one ofthe vehicles 805 to configure according to the configuration(s)contained within the configuration commands 892.

After the configurable payload 815 of the at least one of the vehicles805 has configured according to the configuration commands 892, the atleast one of the vehicles 805 will transmit telemetry (TLM) (e.g.,comprising the configurable payload 815 configuration and the state ofhealth of the at least one of the vehicles 805) 893 to the VOC 825 ofthe GNOC 820, the RNOC 880, and/or the at least one local GW 845.

Then, the at least one local GW 845 and/or the RNOC 880 will transmitkey performance indicators (KPIs) 894, which are obtained from the atleast one of the vehicles (e.g., point of presence (POP)) 805 to theGNOC 820. The KPIs 894 may comprise subscriber demand, MODEM powerprofiles, beam/carrier utilization, session blocking rates, remoteaccess channel (RACH) success rates (e.g., the success rates of the RACHprocedure for handshaking onto the system), bearer success rates (e.g.,the success rates of bearer requests), session setup latency (e.g.,length of time to establish a link), and/or handover success rates (e.g.the success rates for beam-to-beam, vehicle-to-vehicle, and/or userterminal-to-user terminal handover).

In some embodiments, optionally, the RNOC 880 will generate a regionalpolicy 895. The regional policy 895 may comprise admission control,mobility management, channel allocations, carrier allocations, bearerallocations, power management, and/or forward/return (FWD/RTN)scheduling (e.g., downlink/uplink scheduling for user terminals). Forthese embodiments, the RNOC 880 will transmit the regional policy 895 tothe GNOC 820, either directly or via the at least one local GW 845.

After the GNOC 820 has received the KPIs 894, the GNOC 820 will revisethe global policy 891 according to the KPIs 894 and, optionally,according to the regional policy 895.

After the GNOC 820 has revised the global policy 891, the operation ofthe system repeats the steps following the GNOC 820 initially generatingthe global policy 891. As such, the network of the vehicles 805 isself-optimizing by using closed-loop feedback of KPIs 894 (andoptionally the regional policy 895) provided by the at least one localGW 845 and/or the RNOC 880.

FIG. 9 is a block diagram 900 showing the distributed functionalarchitecture for the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback, in accordance with at least oneembodiment of the present disclosure. In this figure, GNOC functions 910and GW functions 920 are illustrated. The GNOC functions 910 arefunctions of the GNOC 820 (refer to FIG. 8), and the GW functions 920are functions of the at least one local GW 845 (refer to FIG. 8) and/orthe RNOC 880 (refer to FIG. 8). As shown in this figure, the GNOCfunctions 910 comprise a message queue 905 and a non-structured querylanguage (No SQL) database 915. In addition, the GNOC functions 910comprise connection management 925 (e.g., for establishing connectionsfrom a user terminal to one of the vehicles 805 within view of the userterminal and to the at least one local GW 845 through the one of thevehicles 805), beam management 935 (e.g., controlling the beamformer,which is located within the one of the vehicles 805 or the at least onelocal GW 845), and carrier management 945 (e.g., controlling thecarriers within a beam). The GNOC functions 910 also comprise aconnection admission control (CAC) policy 930 (e.g., a networkconfiguration policy (e.g., the global policy 891) generated based onuser demand and available resources), routing management 940 (e.g.,controlling the routing of the signal traffic through the network), andsignaling management 950 (e.g., setting up sessions for the routing).

Also in this figure, a resource manager gateway 985 allows for the GNOC820 to communicate with the at least one local GW 845 (or the RNOC 880)via JavaScript Object Notification (JSON) and/or standard web-basedinterfaces (e.g., represented state transfer (REST), hypertext transferprotocol (HTTP), and/or websocket).

As shown in this figure, the GW functions 920 comprise payloadconfiguration (P/L CFG) 955 (e.g., for configuration of the payload),forward link control (F/L CTRL) 965 (e.g., for controlling the linkbetween the vehicle and the at least one local GW 845 (or the RNOC880)), MODEM control 975 (e.g., controlling the MODEM, which creates thecarriers), connection admission control (CAC) 960 (e.g., controlling theadding or removing of user terminals based on the CAC policy 930 (e.g.,global policy 891)), mobility 970 (e.g., controlling the handover ofvehicles as they move and/or of user terminals as they move), andsoftware-defined network (SDN) control 980 (e.g., the routing of signalsaccording to the CAC policy 930).

FIGS. 10A and 10B together form a flow chart showing the method foroperation of the disclosed system for an adaptive self-optimizingnetwork using closed-loop feedback relating to FIG. 8, in accordancewith at least one embodiment of the present disclosure. At the start1010 of the method, a global network operations center (GNOC) receivesoperator inputs, at step 1020. Then, the GNOC generates a global policyaccording to the operator inputs, at step 1030.

The GNOC and/or a local gateway (GW) generate configuration commands forconfigurations for at least one of the vehicles based on the globalpolicy, at step 1040. Then, the GNOC and/or the local GW transmit theconfiguration commands to at least one of the vehicles, at step 1050. Atleast one of the vehicles then transmits telemetry to the GNOC and/orthe local GW, at step 1060.

Then, a local GW transmits key performance indicators (KPIs) to theGNOC, at step 1070. Optionally, a regional network operations center(RNOC) generates a regional policy, at step 1080. The GNOC then revisesthe global policy according to the key performance indicators and,optionally, according to the regional policy, at step 1090. Then, themethod repeats itself by proceeding back to step 1040.

FIG. 11 is a diagram 1100 showing the top level architecture for thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback, in accordance with at least one embodiment of thepresent disclosure. In this figure, a network operation center (NOC)1130 is shown. The NOC 1130 may be a GNOC 820 or a RNOC 880, and may belocated within a GW. The NOC 1130 is shown to comprise an operationalsupport system/business support system (OSS/BSS) 1125 and the operationsmanager 1120. The operations manager 1120 comprises an applicationprogramming interface (API) handler 1135, a database 1140, a SRM policyenforcement module 1145, a TOSCA-based LSO application 1150, and aservice and configuration registry 1155. The operations manager 1120further comprises an operator interface (I/F) 1190 that may be used byan operator 1110 to interface with the operations manager 1120. Inaddition, the operations manager 1120 may operate utilizing LINUX 1160.

The NOC 1130 also comprises a software-defined network (SDN) controller1165, which communicates with the operations manager 1120 by using astandard network management system-software defined network controller(NMS-SDNC) application program interface (API).

Also shown in this figure are an external network 1171 and internalnetworks 1170 a, 1170 b. It should be noted that the system may comprisemore or less than two internal networks 1170 a, 1170 b as is shown inthis figure. The NOC 1130 controls operations of the internal networks1170 a, 1170 b, and the external network 1171 is controlled by adifferent entity.

The external network (Domain B (Peer)) 1171 is shown to comprise anetwork operating system (NOS) 1180 and two routers 1175 a, 1175 b. TheNOS 1180 and the two routers 1175 a, 1175 b are all in communicationwith each other within the external network 1171. Users 1177 bassociated with the external network 1171 are connected to the externalnetwork 1171 via a user-to-network interface (UNI) 1186 d.

The internal network (Domain A₁) 1170 a is shown to comprise a backbonecore bridge (BCB) 1181, a virtual network function (VNF) 1176, a vehicle(e.g., satellite) from the vehicles 805, a provider backbonebridging-traffic engineering (PBB-TE) 1177, and two backbone edgebridges (BEBs) 1182 a, 1182 b. The BCB 1181, VNF 1176, a vehicle fromthe vehicles 805, PBB-TE 1177, and BEBs 1182 a, 1182 b are all incommunication with each other within the internal network 1170 a.

The internal network (Domain A₂) 1170 b is shown to comprise three openvirtual switches (OVSs) 1183 a, 1183 b, 1183 c. The OVSs 1183 a, 1183 b,1183 c are all in communication with each other within the internalnetwork 1170 b. Users 1178 associated with the internal networks 1170 a,1170 b are connected to the internal networks 1170 a, 1170 b viauser-to-network interfaces (UNIs) 1186 a, 1186 b.

The external network 1171 is connected to internal network 1170 a and tointernal network 1170 b via external network-to-network interfaces(ENNIs) 1184 a, 1184 b, 1184 c. Internal network 1170 a is connected tointernal network 1170 b via internal network-to-network interfaces(INNIs) 1185 a, 1185 b.

It should be noted that the external network 1171 and internal networks1170 a, 1170 b may each comprise various different components in variousdifferent combinations than as shown in FIG. 11. In particular, theexternal network 1171 and the internal networks 1170 a, 1170 b may eachcomprise at least one of the vehicles 805, a router 1175, a networkoperating system (NOS) 1180, an open virtual switch (OVS) 1183, abackbone edge bridge (BEB) 1182, a backbone core bridge (BCB) 1181, avirtual network function (VNF) 1176, and/or provider backbonebridging-traffic engineering (PBB-TE) 1177. One or more of the vehicles805 may be a space vehicle, an airborne vehicle, a terrestrial vehicle,or a marine vehicle. In some embodiments, the space vehicle is asatellite, and the satellite is a geosynchronous earth orbit (GEO)satellite, a low earth orbit (LEO) satellite, a medium earth orbit (MEO)satellite, or a super GEO satellite.

During operation of the disclosed system, the operations manager 1120 ofthe NOC 1130 receives a user demand from the external network 1171. Theuser demand specifies a desired amount of resources (e.g., bandwidth,etc.) from the internal networks 1170 a, 1170 b to be used by (sharedwith) users 1179 associated with the external network 1171. Theoperations manager 1120 of the NOC 1130 also receives KPIs from at leastone of the internal networks 1170 a, 1170 b.

After the operations manager 1120 of the NOC 1130 receives the userdemand and the KPIs, the operations manager 1120 of the NOC 1130analyzes the user demand and the KPIs to determine whether at least oneof the internal networks 1170 a, 1170 b has available resources that canbe shared with the users 1177 b. When the operations manager 1120 of theNOC 1130 determines that at least one of the internal networks 1170 a,1170 b has available resources, the operations manager 1120 of the NOC1130 will notify the SDN controller 1165 of the NOC 1130 to allow theusers 1177 b associated with the external network 1171 to connect to theinternal networks 1170 a, 1170 b according to the available resources.The SDN controller 1165 of the NOC 1130 will then allow a specificnumber of users 1177 b to connect to the internal networks 1170 a, 1170b according to the amount of available resources. Then, the users 1177 bthat are allowed to connect to the internal networks 1170 a, 1170 b willproceed to connect to the internal networks 1170 a, 1170 b via UNI 1186c.

It should be noted that the SDN controller 1165 of the NOC 1130 controlsconnections (switching) of the ENNIs 1184, the INNIs 1185, and the UNIs1186 of the system.

FIG. 12 is a diagram 1200 showing further details of the operationsmanager 1120 of FIG. 11, in accordance with at least one embodiment ofthe present disclosure. In this figure, the operations manager 1120 isshown to comprise the database (e.g., system configuration database)1140 (refer to FIG. 11) and further comprise an XML-based configurationdata translator 1210. The database 1140 comprises a startupconfiguration (Cfg) database 1215, a running configuration database1225, and a candidate configuration database 1235. The database 1140receives policy management information, network topology information,service management information, and network state of health andperformance information to be stored within its databases 1215, 1225,1235.

During operation of the disclosed system, the operations manager 1120generates XML models 1220 a, 1220 b, 1220 c, 1220 d, 1220 n forconfigurations for units (e.g., switches 1230 a, routers 1230 b, MODEMs1230 c, and other devices 1230 d) for the configurable payload 815(refer to FIG. 8) according to the global policy 891 (refer to FIG. 8).After the XML models 1220 a, 1220 b, 1220 c, 1220 d, 1220 n have beengenerated, the XML-based configuration data translator 1210 operates asa translator 1240 to translate the XML models 1220 a, 1220 b, 1220 c,1220 d, 1220 n into proprietary flight software commands to be used asthe configuration commands 892 (refer to FIG. 8).

FIG. 13 is a flow chart showing the method for operation of thedisclosed system for an adaptive self-optimizing network usingclosed-loop feedback relating to FIG. 11, in accordance with at leastone embodiment of the present disclosure. At the start 1310 of themethod, a network operations center (NOC) receives user demand for usersfrom an external network, step 1320. Then, the NOC receives keyperformance indicators (KPIs) from at least one internal network, step1330. The NOC then determines whether at least one internal network hasavailable resources by analyzing the key performance indicators and theuser demand, step 1340. When the NOC determines that there are availableresources, the NOC allows at least some of the users from the externalnetwork to connect to at last one internal network to the availableresources, step 1350. Then, at least some of the users from the externalnetwork connect to at least one internal network via at least oneuser-to-network interface (UNI), step 1360. Then, the method ends, step1370.

FIG. 14 is a flow chart showing the method for configuring aconfiguration for a vehicle relating to FIG. 12, in accordance with atleast one embodiment of the present disclosure. At the start 1410 of themethod, XML models are generated for the configuration for the vehicle,step 1420. Then, configuration commands are generated for the vehicleaccording to XML models, step 1430. The configuration of the vehicle isthen configured according to the configuration commands, step 1440.Then, the method ends, step 1450.

Although particular embodiments have been shown and described, it shouldbe understood that the above discussion is not intended to limit thescope of these embodiments. While embodiments and variations of the manyaspects of the invention have been disclosed and described herein, suchdisclosure is provided for purposes of explanation and illustrationonly. Thus, various changes and modifications may be made withoutdeparting from the scope of the claims.

Where methods described above indicate certain events occurring incertain order, those of ordinary skill in the art having the benefit ofthis disclosure would recognize that the ordering may be modified andthat such modifications are in accordance with the variations of thepresent disclosure. Additionally, parts of methods may be performedconcurrently in a parallel process when possible, as well as performedsequentially. In addition, more steps or less steps of the methods maybe performed.

Further, the disclosure comprises examples according to the followingClauses:

Clause 1. A method for sharing network resources, the method comprising:receiving, by a network operations center (NOC), user demand for usersfrom an external network; receiving, by the NOC, key performanceindicators from at least one internal network; determining, by the NOC,whether the at least one internal network has available resources byanalyzing the key performance indicators and the user demand; andallowing, by the NOC when the NOC determines that there are availableresources, at least some of the users from the external network toconnect to the at least one internal network according to the availableresources.

Clause 2. The method of Clause 1, wherein the method further comprisesconnecting at least some of the users from the external network to theat least one internal network via at least one user-to-network interface(UNI).

Clause 3. The method of Clause 1 or 2, wherein the external network isconnected to the at least one internal network via at least one externalnetwork-to-network interface (ENNI).

Clause 4. The method of any one of Clauses 1 to 3, wherein the NOCcontrols operations of the at least one internal network.

Clause 5. The method of any one of Clauses 1 to 4, wherein when thereare more than one of the at least one internal network, the internalnetworks are connected to each other via at least one internalnetwork-to-network interface (INNI).

Clause 6. The method of any one of Clauses 1 to 5, wherein users fromthe at least one internal network are connected to the at least oneinternal network via at least one user-to-network interface (UNI).

Clause 7. The method of any one of Clauses 1 to 6, wherein the externalnetwork and the at least one internal network each comprise at least oneof a vehicle, a router, a network operating system (NOS), an openvirtual switch (OVS), a backbone edge bridge (BEB), a backbone corebridge (BCB), a virtual network function (VNF), or provider backbonebridging-traffic engineering (PBB-TE).

Clause 8. The method of Clause 7, wherein the vehicle is one of a spacevehicle, an airborne vehicle, a terrestrial vehicle, or a marinevehicle.

Clause 9. The method of Clause 8, wherein the space vehicle is asatellite, and wherein the satellite is one of a geosynchronous earthorbit (GEO) satellite, a low earth orbit (LEO) satellite, a medium earthorbit (MEO) satellite, or a super GEO satellite.

Clause 10. The method of any one of Clauses 1 to 9, wherein a softwaredefined network (SDN) controller of the NOC controls connections of atleast one external network-to-network interface (ENNI), at least oneinternal network-to-network interface (INNI), and at least oneuser-to-network interface (UNI).

Clause 11. A system for sharing network resources, the systemcomprising: an external network; at least one internal network; and anetwork operations center (NOC) to receive user demand for users fromthe external network, to receive key performance indicators from the atleast one internal network, to determine whether the at least oneinternal network has available resources by analyzing the keyperformance indicators and the user demand, and to allow, when the NOCdetermines that there are available resources, at least some of theusers from the external network to connect to the at least one internalnetwork according to the available resources.

Clause 12. The system of Clause 11, wherein at least some of the usersfrom the external network are connected to the at least one internalnetwork via at least one user-to-network interface (UNI).

Clause 13. The system of Clause 11 or 12, wherein the external networkis connected to the at least one internal network via at least oneexternal network-to-network interface (ENNI).

Clause 14. The system of any one of Clauses 11 to 13, wherein the NOC isconfigured to control operations of the at least one internal network.

Clause 15. The system of any one of Clauses 11 to 14, wherein when thereare more than one of the at least one internal network, the internalnetworks are connected to each other via at least one internalnetwork-to-network interface (INNI).

Clause 16. The system of any one of Clauses 11 to 15, wherein users fromthe at least one internal network are connected to the at least oneinternal network via at least one user-to-network interface (UNI).

Clause 17. The system of any one of Clauses 11 to 16, wherein theexternal network and the at least one internal network each comprise atleast one of a vehicle, a router, a network operating system (NOS), anopen virtual switch (OVS), a backbone edge bridge (BEB), a backbone corebridge (BCB), a virtual network function (VNF), or provider backbonebridging-traffic engineering (PBB-TE).

Clause 18. The system of Clause 17, wherein the vehicle is one of aspace vehicle, an airborne vehicle, a terrestrial vehicle, or a marinevehicle.

Clause 19. The system of Clause 18, wherein the space vehicle is asatellite, and wherein the satellite is one of a geosynchronous earthorbit (GEO) satellite, a low earth orbit (LEO) satellite, a medium earthorbit (MEO) satellite, or a super GEO satellite.

Clause 20. The system of any one of Clauses 11 to 19, wherein a softwaredefined network (SDN) controller of the NOC is configured to controlconnections of at least one external network-to-network interface(ENNI), at least one internal network-to-network interface (INNI), andat least one user-to-network interface (UNI).

Clause 21. A method for an adaptive network of vehicles, the methodcomprising: receiving, by a global network operations center (GNOC),operator inputs; generating, by the GNOC, a global policy according tothe operator inputs; generating, by at least one of the GNOC or a localgateway (GW), configuration commands for configurations for at least oneof the vehicles based on the global policy; transmitting, by at leastone of the GNOC or the local GW, the configuration commands to at leastone of the vehicles; transmitting, by the local GW, key performanceindicators to the GNOC; and revising, by the GNOC, the global policyaccording to the key performance indicators.

Clause 22. The method of Clause 21, wherein the method further comprisesgenerating, by a regional network operations center (RNOC), a regionalpolicy.

Clause 23. The method of Clause 22, wherein the method further comprisesrevising, by the GNOC, the global policy according to the regionalpolicy.

Clause 24. The method of Clause 22 or 23, wherein the regional policycomprises at least one of admission control, mobility management,channel allocations, carrier allocations, bearer allocations, powermanagement, or forward and/or return (FWD/RTN) scheduling policies.

Clause 25. The method of any one of Clauses 22 to 24, wherein the RNOCis located within a gateway (GW).

Clause 26. The method of any one of Clauses 21 to 25, wherein the GNOC(120) is located within a gateway (GW).

Clause 27. The method of any one of Clauses 21 to 26, wherein the globalpolicy comprises at least one of beam allocations, capacity allocations,software-defined network (SDN) management, or admission control policy.

Clause 28. The method of any one of Clauses 21 to 27, wherein theoperator inputs comprise at least one of frequency spectrum planning,traffic planning, or contingency plans.

Clause 29. The method of any one of Clauses 21 to 28, wherein the keyperformance indicators comprise at least one of subscriber demand, MODEMpower profiles, beam and carrier utilization, session blocking rates,random access channel (RACH) success rates, bearer success rates,session setup latency statistics, or handover success rates.

Clause 30. The method of any one of Clauses 21 to 29, wherein thevehicles are space vehicles, high-altitude platforms, airborne vehicles,terrestrial vehicles, marine vehicles, or fixed terrestrial cellular orwireless base stations.

Clause 31. The method of Clause 30, wherein the space vehicles aresatellites.

Clause 32. The method of Clause 31, wherein the satellites comprise oneof a geosynchronous earth orbit (GEO) satellite constellation, a lowearth orbit (LEO) satellite constellation, a medium earth orbit (MEO)satellite constellation, a supersynchronous GEO satellite constellation,or a hybrid satellite constellation comprising one or moreconstellations or constellation types.

Clause 33. The method of any one of Clauses 21 to 32, wherein the methodfurther comprises: generating, by at least one of the GNOC or the localGW, extensible markup language (XML) models for the configurations forat least one of the vehicles according to the global policy; andgenerating, by at least one of the GNOC or the local GW, theconfiguration commands according to the XML models.

Clause 34. The method of any one of Clauses 21 to 33, wherein the methodfurther comprises transmitting, by at least one of the vehicles,telemetry to at least one of the GNOC or the local GW.

Clause 35. A system for an adaptive network of vehicle, the systemcomprising: a global network operations center (GNOC) configured toreceive operator inputs, to generate a global policy according to theoperator inputs, to generate configuration commands for configurationsfor at least one of the vehicles based on the global policy, and torevise the global policy according to key performance indicators; and alocal gateway (GW) configured to transmit the key performance indicatorsto the GNOC, wherein at least one of the local GW or the GNOC arefurther configured to transmit the configuration commands to at leastone of the vehicles.

Clause 36. The system of Clause 35, wherein the system further comprisesa regional network operations center (RNOC) configured to generate aregional policy.

Clause 37. The system of Clause 36, wherein the GNOC is furtherconfigured to revise the global policy according to the regional policy.

Clause 38. The system of Clause 36 or 37, wherein the regional policycomprises at least one of admission control, mobility management,channel allocations, carrier allocations, bearer allocations, powermanagement, or forward and/or return (FWD/RTN) scheduling policy.

Clause 39. A method for configuring a configuration for a vehicle, themethod comprising: generating XML models for the configuration for thevehicle; generating configuration commands for the vehicle according tothe XML models; and configuring the configuration for the vehicleaccording to the configuration commands.

Clause 40. The method of Clause 39, wherein the XML models are generatedaccording to a global policy.

Clause 41. A system for sharing network resources, the systemcomprising: an external network; at least one internal network; and anetwork operations center (NOC) to perform the method of any one ofClauses 1 to 10.

Clause 42. A system for an adaptive network of vehicle, the systemcomprising: a global network operations center (GNOC) configured toperform the method of any one of Clauses 21 to 34.

Accordingly, embodiments are intended to exemplify alternatives,modifications, and equivalents that may fall within the scope of theclaims.

Although certain illustrative embodiments and methods have beendisclosed herein, it can be apparent from the foregoing disclosure tothose skilled in the art that variations and modifications of suchembodiments and methods can be made without departing from the truespirit and scope of this disclosure. Many other examples exist, eachdiffering from others in matters of detail only. Accordingly, it isintended that this disclosure be limited only to the extent required bythe appended claims and the rules and principles of applicable law.

I claim:
 1. A method for an adaptive network of vehicles, the methodcomprising: receiving, by a global network operations center (GNOC),operator inputs; generating, by the GNOC, a global policy according tothe operator inputs; generating, by at least one of the GNOC or a localgateway (GW), configuration commands for configurations for at least oneof the vehicles based on the global policy; transmitting, by at leastone of the GNOC or the local GW, the configuration commands to at leastone of the vehicles; transmitting, by the local GW, key performanceindicators to the GNOC; and revising, by the GNOC, the global policyaccording to the key performance indicators.
 2. The method of claim 1,further comprising generating, by a regional network operations center(RNOC), a regional policy.
 3. The method of claim 2, further comprisingrevising, by the GNOC, the global policy according to the regionalpolicy.
 4. The method of claim 2, wherein the regional policy comprisesat least one of admission control, mobility management, channelallocations, carrier allocations, bearer allocations, power management,or forward and/or return (FWD/RTN) scheduling policies.
 5. The method ofclaim 2, wherein the RNOC is located within a gateway (GW).
 6. Themethod of claim 5, wherein the GNOC is located within the GW.
 7. Themethod of claim 1, wherein the global policy comprises at least one ofbeam allocations, capacity allocations, software-defined network (SDN)management, or admission control policy.
 8. The method of claim 1,wherein the operator inputs comprise at least one of frequency spectrumplanning, traffic planning, or contingency plans.
 9. The method of claim1, wherein the key performance indicators comprise at least one ofsubscriber demand, MODEM power profiles, beam and carrier utilization,session blocking rates, random access channel (RACH) success rates,bearer success rates, session setup latency statistics, or handoversuccess rates.
 10. The method of claim 1, wherein the at least one ofthe vehicles is a space vehicle, a high-altitude platform, an airbornevehicle, a terrestrial vehicle, a marine vehicle, or a fixed terrestrialcellular or wireless base station.
 11. The method of claim 10, whereinthe space vehicle is a satellite.
 12. The method of claim 11, whereinthe satellite comprises a geosynchronous earth orbit (GEO) satelliteconstellation, a low earth orbit (LEO) satellite constellation, a mediumearth orbit (MEO) satellite constellation, a supersynchronous GEOsatellite constellation, or a hybrid satellite constellation comprisingone or more constellations or constellation types.
 13. The method ofclaim 1, further comprising: generating, by at least one of the GNOC ora local gateway (GW), extensible markup language (XML) models for theconfigurations for the at least one of the vehicles according to theglobal policy; and generating, by at least one of the GNOC or the localGW, the configuration commands according to the XML models.
 14. Themethod of claim 13, further comprising transmitting, by the at least oneof the vehicles, telemetry to at least one of the GNOC or the local GW.15. A system for an adaptive network of vehicles, the system comprising:a global network operations center (GNOC) configured to: receiveoperator inputs; generate a global policy according to the operatorinputs; generate configuration commands for configurations for at leastone of the vehicles based on the global policy; and revise the globalpolicy according to key performance indicators; and a local gateway (GW)configured to transmit the key performance indicators to the GNOC,wherein at least one of the local GW or the GNOC are further configuredto transmit the configuration commands to the at least one of thevehicles.
 16. The system of claim 15, further comprising a regionalnetwork operations center (RNOC) configured to generate a regionalpolicy.
 17. The system of claim 16, wherein the GNOC is furtherconfigured to revise the global policy according to the regional policy.18. The system of claim 17, wherein the regional policy comprises atleast one of admission control, mobility management, channelallocations, carrier allocations, bearer allocations, power management,or forward and/or return (FWD/RTN) scheduling policy.
 19. A method forconfiguring a configuration for a vehicle, the method comprising:generating XML models for the configuration for the vehicle; generatingconfiguration commands for the vehicle according to the XML models; andconfiguring the configuration for the vehicle according to theconfiguration commands.
 20. The method of claim 19, wherein the XMLmodels are generated according to a global policy.